Impact on larger codebases is even more dramatic. For example, I tried testing the performance of spotless:check on real-world projects like apache/flink and aws-java-sdk-v2 by running mvn spotless:check -Dspotless.ratchetFrom=origin/master -Pspotless with the following profile added -

		<profile>
			<id>spotless</id>
			<build>
				<plugins>
					<plugin>
						<groupId>com.diffplug.spotless</groupId>
						<artifactId>spotless-maven-plugin</artifactId>
						<version>3.0.0</version>
						<configuration>
							<ratchetFrom>${spotless.ratchetFrom}</ratchetFrom>
							<java>
								<indent>
									<tabs>true</tabs>
									<spacesPerTab>4</spacesPerTab>
								</indent>
							</java>
						</configuration>
					</plugin>
				</plugins>
			</build>
		</profile>

@nedtwigg

This PR introduces a performance improvement that significantly reduces execution time for large Maven projects. In our case, current Spotless performance makes it impractical to run as part of a Git commit hook, and this change addresses that bottleneck.

Would appreciate a review when you have time. Happy to adjust the approach or provide more benchmarks/validation if needed.